Collapse All Expand All

PrizmDoc installation is designed to be very straightforward for Linux environments. Follow the steps provided in this section.

Some steps may be specific to a particular Linux distribution; these steps will be labeled as being specific to one of the following: 

• "Red Hat / Fedora (CentOS) Linux Distributions"
• "Debian (Ubuntu) Linux Distributions"

 

Step 1 - Download PrizmDoc

Before downloading PrizmDoc, you will need to purchase a license key or request a Trial Evaluation by filling out the following form: www.accusoft.com/products/prizm-content-connect-pcc/get-self-hosted/.

Once you have purchased a license key or filled out the form for a Trial Evaluation, you can download PrizmDoc by:

1. Following the link provided in the response email and selecting the desired Linux Distribution.

OR

2. Downloading directly to the Linux server using the 'wget' command for the specific distribution as shown below:

You must substitute the version of the package you are using in the code examples below. For example, if you are using v11.0, then specify "11.0" instead of "<version>". If the version is a hot fix, you will need to also specify the hot fix number, for example, "11.0.1".

   

Red Hat, Fedora, CentOS, and Older Linux Distributions

Example	Copy Code
wget http://products.accusoft.com/PrizmDoc/<version>/prizmdoc_full_<version>.x86_64.rpm.tar.gz

Debian and Ubuntu Linux Distributions

Example	Copy Code
wget http://products.accusoft.com/PrizmDoc/<version>/prizmdoc_full_<version>.amd64.deb.tar.gz

Generic .tar.gz Distribution

Example	Copy Code
wget http://products.accusoft.com/PrizmDoc/<version>/prizmdoc_full_<version>.x86_64.tar.gz

For license, fill out the form at http://www.accusoft.com/products/prizm-content-connect-pcc/get-self-hosted/ or http://www.accusoft.com/contact/.  

 

Step 2 - Unpack & Install the Downloaded Archive

Open a command line and change to the location where you downloaded the tarball. Use the following command line examples appropriate for your distribution to:

1. Decompress and unpack the downloaded file. After you have unpacked the archive, the contents will have been decompressed into a directory named prizmdoc_full_<version>.<arch>[.rpm|.deb]. 
2. Change to the unpacked directory and install the packages.

Red Hat, Fedora, CentOS, and Older Linux Distributions

The following example is for Red Hat, Fedora, CentOS, and older Linux distributions:

Example	Copy Code
tar -xzvf prizmdoc_full_*.rpm.tar.gz cd prizmdoc_full_*.rpm yum install --nogpgcheck *.rpm

Note: For CentOS 5.x, the following additional dependencies must be installed prior to PrizmDoc RPM installation: openjpeg-libs-1.3-7.el5.x86_64.rpm pixman-0.22.0-2.2.el5_10.x86_64.rpm The Prizm installer does not install them automatically. Please manually download these packages and then install them using --nogpgcheck flag as follows: Example Copy Code yum install --nogpgcheck ./openjpeg-libs-1.3-7.el5.x86_64.rpm yum install --nogpgcheck ./pixman-0.22.0-2.2.el5_10.x86_64.rpm

Debian (Ubuntu) Linux Distributions

The following example is for Debian (Ubuntu) Linux distributions:

Example	Copy Code
tar -xzvf prizmdoc_full_*.deb.tar.gz cd prizmdoc_full_*.deb sudo dpkg --force-depends -i *.deb 'dpkg' does not resolve dependencies automatically, so please ignore possible errors, if you did not install required dependencies yet, and invoke next command sudo apt-get -f install

Generic .tar.gz Distribution

We also provide a generic .tar.gz package. You will need to install the dependencies described in the Requirements section. Once the dependencies are installed, you can install the .tar.gz with the following commands as root:

Example	Copy Code
tar -xzvf prizmdoc_full_*.tar.gz cd prizmdoc_full_* ls prizm-*.tar.gz | xargs -n1 tar zxf cp -R prizm /usr/share/

 

Step 3 - Configure

1. Continuing as root, change to the installation location: /usr/share/prizm and run setup.sh. This will run the Prizm Licensing Utility (PLU) and configure PrizmDoc for its first run:

setup.sh launches the Prizm License Utility (PLU), which is a GUI application. Depending on how you have X11 configured, you might need to run 'xhost +' as the logged in user to allow the PLU launched by the root user to access X11. You can disable X11 access for root by executing 'xhost -' when you are done.

Example

Copy Code

./setup.sh Select the type of license you want to acquire: 1) Evaluation [e] 2) Deployment [d] Choose 1 or 2: d Select the type of deployment license you have: 1) Node Locked [n] 2) OEM [o] Choose 1 or 2: o Provide the solution name: <MySolutionName> Provide the OEM license key provided to you: 2.0... Your deployment license was acquired successfully. ./scripts/pccis.sh start Starting Prizm Content Connect Information Services... Starting PCCIS Watchdog process... PCCIS Watchdog has been started correctly.

2. For a production installation, you will want to configure where log files are stored. See the section How to Configure Log File Locations.  

 

Step 4 - Verify that the Installation was Successful   

1. Browse to the following either via URL or through browser http://localhost:18681/admin:

 

It may take several minutes for PrizmDoc Server to become completely healthy. The page will auto-refresh as PrizmDoc Server come online.

2. Your installation is now complete.

 

Working with Sample Code

Sample code is included to demonstrate how PrizmDoc can be integrated into your Content Management solution. Sample applications using different languages are packaged with the product to demonstrate using a particular language. All of the product samples are located in the "Samples" folder within the installation directory. For more information, refer to the Code Samples topic.

 

How to Install Common Certificate Authority Root Certificates on Linux

The following commands should all be run as root. Additionally, if prompted for addition/removal permission, then yes/no should be entered as the response.

1. Install all Mozilla's root certificates. This command will install all the root certificates Mozilla accepts, prompting only to remove certificates that Mozilla doesn't list, adding all it does trust without prompt. This should make HTTPS work for any system that Firefox works with:

Example	Copy Code
/usr/share/prizm/mono/64/bin/mozroots --machine --import --ask-remove

2. Pull certificates from an https connection to accept:

Example	Copy Code
/usr/share/prizm/mono/64/bin/certmgr -ssl -m https://servertoadd/

As long as the server includes the entire chain to root, this will allow the certificate to authenticate. This will generally be the case for self-signed test certificates. For more complex situations, any required items from the chain will need to be added manually.

3. Manually add the certificate from the file:

Example	Copy Code
/usr/share/prizm/mono/64/bin/certmgr -add -c -m /path/to/certificatefile

The certificate stores the certificates at: /usr/share/.mono/certs/.

 

Enabling Upload of Larger Files

By default /usr/share/prizm/pccis/servicehost/host.config contains the following limitation:

Example	Copy Code
/usr/share/prizm/pccis/servicehost/host.config "httpRuntime": { ... "maxRequestLength": 50000000 }

which limits maximum document file size to 50Mb, and so PCCIS will return HTTP-500 when larger files are uploaded to the service. If you are dealing with larger files it will necessary to change the "maxRequestLength" option to a more appropriate value.

 

 

---

©2016. Accusoft Corporation. All Rights Reserved.

Send Feedback